Authenticating activities of accounts

ABSTRACT

A system, a medium, and a method involve a communication interface of a server device that receives first activity data associated with a first activity of an account and second activity data associated with a second activity of the account. A processor of the server device determines a first location of the first activity from the first activity data and a second location of the second activity from the second activity data. An authentication circuit of the server device determines a first authentication of the first activity based at least on the first activity data. The authentication circuit determines a second authentication of the second activity based on at least one of the first authentication, the first location, and the second location. A transmitter of the communication interface transmits an indication of the second authentication to a client device.

TECHNICAL FIELD

This disclosure relates to authenticating one or more activities of anaccount, and more particularly, to computing devices configured todetermine authentications of one or more activities.

BACKGROUND

Some examples of accounts may include financial accounts, e-mailaccounts, social networking accounts, e-commerce accounts, accounts withservice providers, and/or other types of accounts. Various technologiesmay evaluate activities of an account. In some instances, passwords,ciphers, digital keys, and/or other codes may validate the activities ofthe account. For example, an automated teller machine (ATM) may beconfigured to receive ATM card data and a personal identification number(PIN) to identify a financial account and validate activities of theaccount. Further, a fuel dispenser machine at a gas station may beconfigured to receive credit card data and a zip code to identify afinancial account and validate fuel purchases made with the account.

In some instances, a user may have to keep track of multiple ATM cards,credit cards, identification cards, passwords, PIN numbers, zip codes,and/or other forms of account data to validate activities of one or moreaccounts. In addition, the user may be required to periodically changesuch cards, passwords, codes, and/or accounts to prevent unauthorizedactivities by other users. As such, it may be necessary to keep track ofmultiple changes to such cards, passwords, codes, and/or accounts,possibly requiring data maintenance, security, and/or protection of suchaccounts. In some embodiments, various sophisticated technologies may beimplemented to reduce and/or eliminate the need for such requirements.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified block diagram of an example system, according toan embodiment;

FIG. 2A provides an exemplary server device configured to support a setof trays, according to an embodiment;

FIG. 2B provides an exemplary tray configured to support one or moreserver components, according to an embodiment;

FIG. 3 provides an exemplary system, according to an embodiment;

FIG. 4 provides an exemplary system, according to an embodiment;

FIG. 5 is a flowchart of an exemplary method for determiningauthentications of activities, according to an embodiment;

FIG. 6 provides an exemplary client device with a user interface,according to an embodiment;

FIG. 7A provides an exemplary client device, according to an embodiment;

FIG. 7B provides another exemplary client device, according to anembodiment;

FIG. 8 is an illustration of various authentication schemes, accordingto an embodiment;

FIG. 9 provides an exemplary system, according to an embodiment;

FIG. 10 provides an exemplary system, according to an embodiment;

FIG. 11 provides an exemplary client device with a user interface,according to an embodiment; and

FIG. 12 is a flowchart of an exemplary method for determining anauthentication scheme to authenticate activities.

Embodiments of the present disclosure and their advantages are bestunderstood by referring to the detailed description that follows. Itshould be appreciated that reference numerals are used to identifyelements illustrated in one or more of the figures, where showingstherein are for purposes of illustrating embodiments of the presentdisclosure and not for purposes of limitation.

DETAILED DESCRIPTION

In some embodiments, various activities of a user's account may beauthenticated. In some instances, the activities may be authenticatedbased on a location of the user's smartphone. For example, consider ascenario where the user carries the smartphone from a home to a nearbyvehicle. As such, an authentication system may receive location dataindicating that the user is leaving the home location and carrying thesmartphone to the nearby vehicle. Further, the system may identify aroute of the smartphone from the home location to an ATM machine a fewmiles away. The system may further identify the route is often taken toaccess the user's account with the ATM machine. The system may alsoidentify the ATM machine as one regularly used to access the user'saccount. Based on the identified route, the user swiping an ATM card atthe ATM machine and entering a valid PIN number, the system maydetermine a successful authentication of the user's activity, enablingthe ATM machine to access the user's account. Yet, in some instances,the system may determine a successful authentication based on theidentified route, the identified ATM machine, and a valid PIN number,thereby circumventing the need to swipe the card at the ATM machine. Assuch, the user may securely access the account without having to swipethe card to access the account, let alone having to carry the card.

In some embodiments, the system may authenticate activities of theaccount based on various confidence levels. For example, considering thescenario above, the system may determine a confidence level toauthenticate additional activities of the account based on theidentified route to the ATM machine and the successful authentication atthe ATM machine. In another scenario, consider the system identifies achange in the location of the smartphone to a nearby gas stationregularly used to purchase fuel with the user's account. In someinstances, the system may enable the user to purchase fuel at the gasstation based on the determined confidence level. For example, thesystem may enable a fuel dispenser to allow a fuel purchase by receivingbiometric data from the user. Thus, the user may press a finger on afingerprint sensor of the dispenser machine and begin refueling theuser's vehicle. Thus, based on determined confidence levels, the systemmay authenticate activities through biometric data, thereby allowing theuser to refuel the vehicle without carrying ATM cards and/or creditcards. Further, the system may authenticate activities of the accountwithout prompting the user for a PIN number, a zip code, a password,and/or other forms of account data.

In some embodiments, the authentication system may authenticateactivities of multiple related accounts. For example, considering one ormore scenarios above, the system may identify a change in location ofthe user's smartphone to a shopping mall location. Further, the systemmay receive location data from another smartphone, e.g., a smartphonecarried by the user's spouse, indicating the spouse's smartphone is alsolocated at the shopping mall. In some instances, based on the closeproximity of the user's smartphone to the spouse's smartphone, thesystem may determine a confidence level to authenticate additionalactivities of the user's account and/or the spouse's account. The systemmay enable the stores in the shopping mall to allow the spouse to makepurchases based on the spouse's biometric data. For example, the storesmay allow purchases by receiving data corresponding to a singlethumbprint from the spouse, thereby allowing the spouse to shop withoutcarrying ATM cards, credit cards, driver's licenses, and/or other cards.Further, the system may authenticate activities of the spouse's accountwithout requiring a PIN number, a zip code, a password, and/or otherforms of account data.

In some embodiments, various types of data may include activity data,authentication data, biometric data, location data, and/or other typesof data. In some instances, various types of data may be represented bypackets of data, possibly referred to as “data packets.” In someinstances, a server may manage data packets indicative of activities ofaccounts, and the server may transmit data packets to a client device(e.g., a smartphone). For example, consider one or more scenarios abovewhere a smartphone is moved from the home location to the location ofthe vehicle. In such instances, a server device may receive activitydata associated with the smartphone moving from the home location to thevehicle location. Further, the server device may transmit to thesmartphone activity data indicating the change in locations. As such,the activity data may be shown on a display of the smartphone.

FIG. 1 is a simplified block diagram of an example system 100, accordingto an embodiment. As shown, the system 100 includes multiple computingdevices, such as a server device 102, a client device 104, a clientdevice 106, and/or other computing devices. The server device 102 may beconfigured to support, operate, run, and/or manage various forms ofactivity data, authentication data, biometric data, location data,and/or other types of data. As such, also included in the system 100 isa communication network 108. The system 100 may operate with more orless than the computing devices shown in FIG. 1, possibly communicatingwith such devices via a communication network 108. In variousembodiments, the server device 102, the client device 104, and/or theclient device 106 may be configured to communicate via the communicationnetwork 108.

In some embodiments, the communication network 108 may be apacket-switched network configured to provide digital networkingcommunications and exchange data of various forms, content, type, and/orstructure. The communication network 108 may correspond to small scalecommunication networks, such as a private or local area network, or alarger scale network, such as a wide area network or the Internet,accessible by the various computing devices of the system 100. Thecommunication network 108 may include network adapters, switches,routers, network nodes, and various buffers and queues to exchange datapackets. For example, the communication network 108 may be configured toexchange data packets such as a first data packet 126 and/or a seconddata packet 128 including activity data, authentication data, biometricdata, location data, and/or other types of data. The communicationnetwork 108 may exchange data packets between the server device 102, theclient device 104, and/or the client device 106 using various protocolssuch as Transmission Control Protocol/Internet Protocol (TCP/IP), amongother possibilities.

In some embodiments, the system 100 may also include other computingdevices and/or software configured to perform various operations inaccordance with this disclosure and illustrated by the accompanyingfigures. For example, the system 100 may include other client devices,servers including stand-alone and/or enterprise-class servers, serversimplementing one or more operating systems such as a client- and/orserver-based operating systems. It can be appreciated that the clientdevices and/or server devices illustrated in FIG. 1 may be deployed inother ways and that the operations performed and/or the servicesprovided by such devices may be combined or separated for a givenembodiment and may be performed by a greater number or a fewer number ofdevices and/or server devices. One or more devices and/or server devicesmay be operated and/or maintained by the same or different entities.

In some embodiments, the system 100 may include the server device 102configured to perform various implementations in accordance with thisdisclosure and illustrated by the accompanying figures. For example, theserver device 102 may be configured to receive and/or access activitydata associated with various activities of an account. Further, theserver device 102 may be configured to receive and/or access activitydata associated with various activities of multiple accounts. Forexample, the server device 102 may be configured to receive and/oraccess location data identifying the locations of the client device 104and/or 106.

In some embodiments, an “account” and/or a “user account” may be acompilation of data associated with activities. As noted, some examplesof accounts may include financial accounts, e-mail accounts, socialnetworking accounts, e-commerce accounts, smartphone accounts, and/oraccounts with service providers, among other possibilities. For example,an account for a particular user may include data related to the user'sactivities and/or data representing the user. The user may providevarious types of information to the account. The account may bedisplayed on a computing device, such as a smartphone, a laptopcomputer, and/or a wearable computing device that may be used to accessthe account. The user may operate the computing device and their accountmay be managed on the computing device. For example, the computingdevice may receive data, send data, and/or store data associated withthe account. For example, details regarding various activities may beviewed on the computing device. Further, various types of data may beprovided to authenticate the account and payment information may beprovided secure transactions with the account.

In some embodiments, the account may gather data regarding the user andcompile the data into the user's account. In particular, the account maytrack previous activities associated with the account, locations of theactivities, purchases made with the account, and/or other forms ofactivity data indicative of future activities that may be associatedwith the account. Further, the account may track how long it takes theuser to participate in activities, e.g., shopping and/or purchasingitems. The account may also provide recommendations to the user based onthe information stored in the user's account.

In some embodiments, an account may be created by one or more users.Further, the account may be created by applications, web sites, and/orother services, for instance. Thus, various users may have access to aparticular account. The user may be an entity, and/or a corporation,among other possibilities. For example, the user may be a corporationwith access to a corporate account, possibly for its employees and/orcontractors. Yet further, a user may be a computing device, a computingsystem, a robotic system, and/or another form of technology capable ofsending and receiving information using the account. A user may providea login, a password, a code, authentication data, biometric data, and/orother types of data to access the account.

In some embodiments, a user may have a single account providing arepresentation of the user for various websites, applications, and/orother services. For example, a user could opt to use their e-mailaccount or social network account as a multi-purpose account to useand/or access financial accounts, e-commerce accounts, service accountsand/or other types of accounts. For example, a single account may beused to perform various activities and/or services. For example, theaccount may track locations of the user, enable withdrawals and/ordeposits of cash via an ATM machine, allow purchasing of store items,and/or enable other activities. In some instances, the user may beprompted for various types of authentication data and submit therequisite data to proceed with the account activities.

In some embodiments, the server device 102 may take a variety of formsand may include various components, including for example, acommunication interface 112, a transceiver 114, a processor 116, a datastorage 118, an authentication circuit/component 120, and/or othercircuits/components, any of which may be communicatively linked to theother modules via a system bus, network, or other connection mechanism124.

The communication interface 112 may take a variety of forms and may beconfigured to allow the server device 102 to communicate with one ormore devices according to any number of protocols. For example, thecommunication interface 112 may include the transceiver 114 configuredto allow the server device 102 to communicate with the client devices104 and/or 106 via communication network 108. In one example, thecommunication interface 112 and/or the transceiver 114 may take the formof a wired interface, such as an Ethernet interface. As another example,the communication interface 112 and/or the transceiver 114 may take theform of a wireless interface, such as a cellular interface, a WI-FIinterface, another short-range, point-to-multipoint voice and/or datatransfer communication interface, such as BLUETOOTH. In some instances,the communication interface 112 may send/receive activity data to/fromclient devices 104 and/or 106.

The processor 116 may include or take the form of a general purposeprocessor, e.g., a microprocessor. Further, the processor 116 mayinclude a special purpose processor such as a digital signal processor(DSP), an application specific integrated circuit (ASIC), a programmablesystem on chip, and/or another processing component configured toprocess activity data, authentication data, biometric data, locationdata, and/or other types of data. As such, the processor 116 may receivedata and/or data packet 126 via the communication network 108. Further,the processor 116 may access data and/or data packet 128 received by theserver device 102. For example, the data packet 126 and the data packet128 may be transmitted over communication network 108. Further, the datapackets 126 and 128 may include IP addresses of client device 104 and106, respectively. Yet further, the data packets 126 and/or 128 may alsoinclude data in protocols such as Transmission Control Protocol/InternetProtocol (TCP/IP). In various embodiments, each of packets 126 and 128may include 1,000 to 1,500 bytes, among other possible data capacityranges.

The data storage 118 may include one or more volatile, non-volatile,removable, and/or non-removable storage components, such as magnetic,optical, or flash storage, and may be integrated in whole or in partwith processor 116. Further, the data storage 116 may include or takethe form of a non-transitory computer-readable storage medium, havingstored thereon machine-readable instructions (e.g., compiled ornon-compiled program logic and/or machine code) that, when executed byserver device 102, cause the server device 102 to perform operations,such as those described in this disclosure and illustrated by theaccompanying figures.

The processor 116 may determine one or more locations of activities fromactivity data. Further, the processor 116 may determine that activitydata includes authentication data such as biometric data. In someinstances, the processor 116 may include pre-configured and/or dedicatedcircuits of server device 102. Further, the processor 116 may includecircuits and/or hardware components configured to carry out operationsin accordance with this disclosure and illustrated by the accompanyingfigures. For example, the processor 116 may determine from the data 126a first location of a first activity. Yet further, the processor 116 maydetermine from the data 128 a second location of a second activity.

The authentication circuit and/or component 120 may determine variousauthentications of activities based on authentication data such asbiometric data. The authentication circuit and/or component 120 may alsodetermine relationships between accounts. The authentication circuitand/or component 120 may also determine authentication schemes toauthenticate activities of accounts. In some instances, theauthentication circuit and/or component 120 may include pre-configuredcircuits, dedicated circuits, and/or hardware components of serverdevice 102 to determine authentication data, relationships,authentication schemes, authentications of activities, and/or other datarelated to authenticating activities of accounts. Further, theauthentication circuit and/or component 120 may include circuits and/orhardware components configured to carry out operations in accordancewith this disclosure and illustrated by the accompanying figures. Forexample, the authentication circuit and/or component 120 may determine afirst authentication of a first activity based on the first activitydata 126 and a second authentication of a second activity based on thesecond activity data 128.

As with server device 102, client devices 104 and 106 may be configuredto perform a variety of operations such as those described in thisdisclosure and illustrated by the accompanying figures. For example,client devices 104 and 106 may be configured to exchange activity datawith the server device 102 such as data 126 and 128 indicatingactivities associated with accounts. Client devices 104 and 106 may takea variety of forms, including for example, a personal computer (PC), asmartphone, a wearable computer, a laptop/tablet computer, a merchantdevice, a smart watch with appropriate computer hardware resources, ahead-mountable display, other types of wearable devices, and/or othertypes of computing devices capable of transmitting and/or receivingdata, among other possibilities. Client devices 104 and 106 may includevarious components, including, for example, user interfaces 130 and 140,communication interfaces 132 and 142, processors 134 and 144, and/ordata storages 136 and 146, respectively, all of which may becommunicatively linked with each other via a system bus, network, orother connection mechanisms 138 and 148, respectively.

User interfaces 130 and 140 may be configured for facilitatinginteraction between client devices 104 and 106 and users of clientdevices 104 and 106. For example, user interfaces 130 and/or 140 may beconfigured to receive inputs from respective users and providing outputsaccordingly. In some instances, the user interfaces 130 and 140 mayinclude input components such as a touchscreen, a touch sensitive panel,a microphone for receiving voice commands, a computer mouse, a keyboard,and/or other input components. In addition, user interfaces 130 and 140may include output components such as displays possibly with touchscreeninputs, a sound speaker and/or other audio output mechanism, a hapticfeedback system, and/or other output components.

In some embodiments, communication interfaces 132 and 142 may take avariety of forms and may be configured to allow client devices 104 and106, respectively, to communicate with one or more devices according toany number of protocols. For instance, communication interfaces 132 and142 may be configured to allow client devices 104 and 106, respectively,to communicate with the server device 102 via the communication network108.

Processors 134 and 144 may include general purpose processors and/orspecial purpose processors. Data storages 136 and 146 may include one ormore volatile, non-volatile, removable, and/or non-removable storagecomponents, and may be integrated in whole or in part with processors134 and 144, respectively. Further, data storages 136 and 146 may takethe form of non-transitory computer-readable storage mediums, havingstored thereon machine-readable instructions that, when executed byprocessors 134 and 144, cause client devices 104 and 106 to performoperations, respectively, such as those described in this disclosure andillustrated by the accompanying figures. Such machine-readableinstructions may define or be part of a discrete software application,such a native app and/or web app that can be executed upon user input.

FIG. 2A is an exemplary server device 200 configured to support a set oftrays, according to an embodiment. The server device 200 may, forexample, take the form of the server device 102 described above inrelation to FIG. 1. Further, the server device 200 may be configured tosupport, operate, run, and/or manage activity data, authentication data,biometric data, location data, and/or other types of data.

As shown, the server device 200 may include a chassis 202 that maysupport trays 204 and 206, and possibly multiple other trays as well.The chassis 202 may include slots 208 and 210 configured to hold thetrays 204 and 206, respectively. For example, the tray 204 may beinserted into the slot 208 and the tray 206 may be inserted into theslot 210. Yet, the slots 208 and 210 may be configured to hold the trays204 and 206 interchangeably such that the slot 208 may be configured tohold the tray 206 and the slot 210 may be configured to hold the tray204. For example, the tray 204 may be inserted into the slot 208 and thetray 206 may be inserted into the slot 210. Further, during operation ofthe server device 200, the trays 204 and 206 may be removed from theslots 208 and 210, respectively. Yet further, the tray 204 may beinserted into the slot 210 and the tray 206 may be inserted into slot208, and the server device 200 may continue various operations.

The chassis 202 may be connected to a power supply 212 via connections214 and 216 to supply power to the slots 208 and 210, respectively. Thechassis 202 may also be connected to communication network 218 viaconnections 220 and 222 to provide network connectivity to the slots 208and 210, respectively. As such, trays 204 and 206 may be inserted intoslots 208 and 210, respectively, and power supply 212 may supply powerto trays 204 and 206 via connections 214 and 216, respectively. Further,trays 204 and 206 may be inserted into slots 210 and 208, respectively,and power supply 212 may supply power to trays 204 and 206 viaconnections 216 and 214, respectively. Yet further, trays 204 and 206may be inserted into slots 208 and 210, respectively, and communicationnetwork 218 may provide network connectivity to trays 204 and 206 viaconnections 220 and 222, respectively. In addition, trays 204 and 206may be inserted into slots 210 and 208, respectively, and communicationnetwork 218 may provide network connectivity to trays 204 and 206 viaconnections 222 and 220, respectively.

The communication network 218 may, for example, take the form ofcommunication network 108 described above in relation to FIG. 1. In someembodiments, communication network 218 may provide a network port, anetwork hub, a network switch, or a network router that may be connectedto a telephone, Ethernet, or an optical communication link, among otherpossibilities.

FIG. 2B illustrates an exemplary tray 204 configured to support one ormore server components, according to an embodiment. The tray 204 may,for example, take the form of tray 204 described above in relation toFIG. 2A. Further, the tray 206 may also take the form of the tray 204.As shown in FIG. 2B, the tray 204 may include a tray base 230 that maybe the bottom surface of the tray 204 configured to support multiplecircuits and/or circuit components such as a main computing boardconnecting various other components. The tray 204 may include aconnector 226 that may link to the connections 214 or 216 to supplypower to the tray 204. The tray 204 may also include a connector 228that may link to the connections 220 or 222 to provide networkconnectivity to the tray 204. The connectors 226 and 228 may bepositioned on the tray 204 such that upon inserting the tray 204 intothe slot 208, the connectors 226 and 228 couple directly with theconnections 214 and 220, respectively. Further, upon inserting tray 204into slot 210, connectors 226 and 228 may couple directly withconnections 216 and 222, respectively.

The tray 204 may include components 232, 234, 236, 238, and 240. In someinstances, a communication interface 232, a transceiver 234, a processor236, data storage 238, and an authentication circuit and/or component240 may, for example, take the form of the communication interface 112,the transceiver 114, the processor 116, the data storage 118, and theauthentication circuit and/or component 120, respectively. As such, thetray 204 may provide power and network connectivity to each ofcomponents 232-240. In some embodiments, one or more of the components232-240 may be provided via one or more circuits and/or components thatinclude resistors, inductors, capacitors, voltage sources, currentsources, switches, logic gates, registers, and/or a variety of othercircuit elements. One or more of the circuit elements in a circuit maybe configured to provide the circuit(s) that cause one or more of thecomponents 232-240 to perform the operations described herein. As such,in some embodiments, preconfigured and dedicated circuits may beimplemented to perform the operations of the components 232-240. Inother embodiments, a processing system may execute instructions on anon-transitory, computer-readable medium to configure one or morecircuits to perform operations described herein and illustrated by theaccompanying figures.

Any of the circuits and/or components 232-240 may be combined to takethe form of one or more general purpose processors, microprocessors,and/or special purpose processors, among other types of processors. Forexample, one or more of the communication interface 232, the transceiver234, the processor 236, the data storage 238, and the authenticationcircuit and/or component 240 may be combined, possibly such that thecommunication interface 232, the transceiver 234, the data storage 238,and the authentication circuit and/or component 240 are combined with orwithin the processor 236. Further, the combined processor 236 may takethe form of one or more processors, microprocessors, special purposeprocessors, DSPs, GPUs, FPUs, network processors, and/or ASICs, amongother types of processing components. Yet further, the combinedprocessor 236 may be configured to carry out various operations of thecommunication interface 232, the transceiver 234, the data storage 238,and the authentication circuit and/or component 240.

In some embodiments, the communication interface 232 of the serverdevice 202 may receive first activity data associated with a firstactivity of an account and second activity data associated with a secondactivity of the account. The first and second activities may occur atdifferent times. The processor 236 of the server device 202 maydetermine a first location of the first activity from the first activitydata and a second location of the second activity from the secondactivity data. For example, the processor 236 may identify GPS data inthe first and second activity data to determine the first and secondlocations, respectively. The authentication circuit and/or component 240of the server device may determine a first authentication of the firstactivity based at least on the first activity data. For example, thefirst activity data may include ATM card data from swiping a valid cardand entering a valid pin number. Further, the authentication circuitand/or component 240 may determine a second authentication of the secondactivity based on at least one of the first authentication, the firstlocation, and the second location. The transceiver 234 of thecommunication interface may transmit an indication of the secondauthentication to a client device, e.g., a smartphone.

In some embodiments, the communication interface 232 of the serverdevice 202 may receive a selection of an authentication scheme toauthenticate activities of an account. Further, the communicationinterface 232 may receive activity data associated with a given activityof the account. The processor 236 of the server device 202 may determinethe activity data includes biometric data to authenticate the givenactivity of the account. The authentication circuit and/or component 240of the server device 202 may determine the authentication scheme isselected from a number of authentication schemes, where the selectedauthentication scheme requires the biometric data to authenticate theactivities of the account. Further, the authentication circuit and/orcomponent 240 may determine an authentication of the given activitybased at least on the biometric data. The transceiver 234 of thecommunication interface 232 may transmit an indication of theauthentication to a client device such as the smartphone.

FIG. 3 is an exemplary system 300, according to an embodiment. As shown,activities 302 and 304 may involve a smartphone 306 and a vehicle 308.For example, considering one or more of the scenarios above, the system300 may determine the activity 302 of a user leaving a home location andcarrying the smartphone 306 to the vehicle 308. Further, the activity302 may include the user entering the vehicle 308 at a location 314provided on a map 316 for illustrative purposes. The smartphone 306 may,for example, take the form of any of the client devices described abovein relation to FIGS. 1-2B. For example, the client device 306 may takethe form of client device 104 such that activity data 310 may bedisplayed on the user interface 130. Thus, the user interface 130 mayinclude a display component configured to display the activity data 310.

In some embodiments, the system 300 may include a communicationinterface, a transceiver, a processor, data storage, an authenticationcircuit/component of a server device that may take the form of thecommunication interfaces 112 and/or 232, the transceivers 114 and/or234, the processors 116 and/or 236, the data storage 218 and/or 238, andthe authentication circuit/component 120 and/or 240 of the serverdevices 100 and/or 200, respectively, described above in relation toFIGS. 1-2B.

In some embodiments, the communication interface of the server devicemay receive the first activity data 310 associated with a first activity302 of an account and second activity data 312 associated with a secondactivity 304 of the account. For example, the first activity data 310may include location data, e.g., GPS data, indicative of the location314 and/or the location of the vehicle 308. Further, the first activitydata 310 may include other data associated with the vehicle 308, e.g.,BLUETOOTH data pairing the smartphone 306 with the vehicle 308, and/orother data related to activity 302. The second activity data 312 mayinclude data indicative of a fuel purchase via a fuel dispenser machine320 of a gas station. Further, the second activity data 312 may includeGPS data indicative of the location 318, contact data of the gas stationincluding address and phone data of the gas station.

In some embodiments, the processor of the server device may determine afirst location 314 of the first activity 302 from the first activitydata 310 and a second location 318 of the second activity 304 from thesecond activity data 312. As noted, the first location 314 and thesecond location 318 may be shown on the map 316 for illustrationpurposes. In some instances, the first location 314 and the secondlocation 318 may be a few miles apart. Further, the authenticationcircuit of the server device may determine a first authentication of thefirst activity 302 based at least on the first activity data 310. Forexample, the authentication circuit may determine the user leaving thehome location and carrying the smartphone 306 to the vehicle 308 basedon the first activity data 310, e.g., GPS data indicative of thelocation 314. Further, the authentication circuit of the server devicemay determine a second authentication of the second activity 304, e.g.,the fuel purchase, based on at least one of the first authentication,the first location 314, and/or the second location 318. The transmitterof the communication interface may transmit an indication of the secondauthentication to a client device, e.g., the smartphone 306. Yetfurther, the indication of the second authentication may be transmittedto a merchant device, for example, the fuel dispenser 320.

In some embodiments, the authentication circuit may determine the firstauthentication is a successful authentication of the first activity 302based at least on the first activity data 310. For example, theauthentication circuit may determine the user carrying the smartphone306 to the vehicle 308 based on the first activity data 310 includingGPS data indicative of the location 314. Further, the authenticationcircuit may determine the second authentication is a successfulauthentication of the second activity 304 of the fuel purchase, based atleast on the successful authentication of the first activity 302 of theuser carrying the smartphone 306 to the vehicle 308.

In some embodiments, the processor may determine that the secondactivity data 312 includes biometric data to authenticate the secondactivity. In some instances, the user may enter a zip code to the fueldispenser machine 320 and/or the smartphone 306 to complete the fuelpurchase. Yet, in some instances, the user may provide biometric datasuch as fingerprint data via the fuel dispenser machine 320 and/or thesmartphone 306 to complete the fuel purchase. In addition, theauthentication circuit may determine the second authentication is asuccessful authentication of the second activity 304 based at least onthe biometric data.

In some embodiments, the authentication circuit may determine a route322 located between the first location 314 and the second location 318.Further, the authentication circuit may determine the secondauthentication of the second activity 304 based at least on the route322. For example, the authentication circuit may determine the route 322includes one or more stored routes and/or historical routes associatedwith the account. For example, the route 322 may have been previouslytaken to complete fuel purchases at one or more fuel dispenser machines320 at the location 318. Further, the route 322 may have been previouslytaken to make other purchases, e.g., restaurant food, groceries, and/orother regularly purchased items, in the area surrounding the location318.

In some embodiments, the authentication circuit may determine the route322 located between the first location 314 and the second location 318.Further, the authentication circuit may determine a confidence level toauthenticate the second activity 304 based at least on the route 322. Insome instances, the authentication circuit may determine the confidencelevel based on the route 322 including the one or more stored routesand/or historical routes. For example, the authentication circuit maydetermine a high confidence level to authenticate the second activity304 based on the route 322 including one or more stored routes and/orhistorical routes. In some embodiments, the authentication circuit maydetermine the second authentication is a successful authentication ofthe second activity 304 based at least on the confidence level.

In some embodiments, the authentication circuit may determine variousconfidence levels based on the route 322 to authenticate activities ofthe account. For example, the authentication circuit may compare theroute 322 with stored routes and/or historical routes associated withthe user's account and/or other accounts such as a spouse's accountsand/or a friend's account. The authentication circuit may determine aconfidence level based on the route 322 matching one or more portions ofthe stored routes and/or historical routes and/or the route 322 matchinga given percentage of such routes. Further, the authentication circuitmay determine the confidence level based on a number of occasions ortimes in which the user has taken the route 322, possibly to reach oneor more locations near the location 318. Yet further, the authenticationcircuit may determine the confidence level based on the time, the day,and/or the week the user takes the route 322 in comparison to storedand/or historical times, days, and/or weeks associated with such routes.In addition, the authentication circuit may determine the confidencelevel based on the proximity of the route 322 with the location 314 ofthe user's home location and/or the location 318 that may be near anoffice associated with the user's account. Further, the authenticationcircuit may determine the confidence level based on a calendar eventassociated with the user's account. In one scenario, the authenticationcircuit determines the route 322 may be taken to reach the location 318near the user's dental office for a scheduled appointment on a Thursdaymorning, for example.

In some embodiments, one or more confidence thresholds may be determinedand/or pre-determined to authenticate activities of the account. In someinstances, the confidence threshold may be pre-determined by the userand/or the system 300. For example, the confidence threshold may be aneighty-five percent threshold such that the confidence levels associatedwith an activity must meet or exceed this threshold to authenticate theactivity. Thus, in some instances, the authentication circuit maydetermine the confidence level meets the confidence threshold. Further,in some instances, the authentication circuit may determine the secondauthentication is a successful authentication of the second activity 304based at least on the confidence level determined to meet the confidencethreshold. In some embodiments, the authentication circuit may determinethe confidence level is below a confidence threshold. Further, theauthentication circuit may determine the second authentication is afailed authentication of the second activity 304 based at least on theconfidence level determined to be below the confidence threshold.

In some embodiments, the confidence threshold may change based onvarious factors. For example, the confidence threshold may increasebased on the activity of the account. The confidence threshold mayincrease based on the activity including one or more monetarywithdrawals from the account. The confidence threshold may decreasebased on the activity including one or more money deposits to theaccount. Further, the confidence threshold may increase or decreasebased the activity occurring proximate to the location 314 and/or theuser's home location. The confidence threshold may increase or decreasebased on the activity occurring proximate to the location 318.

In some embodiments, the authentication circuit may determine the route322 taken by the smartphone 306 is located between the first location314 and the second location 318. Further, the authentication circuit maydetermine that the route 322 indicates one or more stored routes and/orhistorical routes associated with the account. Yet further, the route322 may be one of a number of historical routes associated with theaccount. In some embodiments, the authentication circuit may determine aconfidence level to authenticate the second activity 304 based at leaston the route 322 indicative of the historical route. Further, theauthentication circuit further may determine the second authenticationis a successful authentication of the second activity 304 based at leaston the determined confidence level, possibly meeting or exceeding aconfidence threshold described above.

FIG. 4 is an exemplary system 400, according to an embodiment. As shown,activities 402 and 404 may involve client devices 406 and/or 408. Forexample, considering one or more of the scenarios above, the system 400may determine an activity 402 of a user carrying the client device 406,e.g., a smartphone, proximate to structures 422, 424, 426, and/or 428provided on a map 420 for illustrative purposes. Further, the system 400may determine an activity of another user, e.g., the user's spouse,carrying the client device 408, e.g., a smartphone, proximate to thestructures 420, 422, 424, and/or 426. Further, the system 400 mayreceive location data of the spouse's location from the smartphone 408.In some instances, based on the relationship between the user's accountand the spouse's account, various stores in the structures, e.g., 420,422, 424, and/or 426, may allow purchases from the user's account and/orthe spouse's account using biometric data. For example, the stores mayallow purchases by receiving data corresponding to a single thumbprintfrom the user and/or the spouse, thereby circumventing the need forproviding various cards, codes, and/or other forms of account data.Further, in some embodiments, biometric data may be substituted forand/or replaced by other types of authenticating data, such as entry ofa PIN number or performance of a gesture.

The smartphones 406 and 408 may, for example, take the form of any ofthe client devices 104 and 106, respectively, described above inrelation to FIGS. 1-3. For example, the client devices 406 and 408 maytake the form of client devices 104 and 106, respectively, such thatdata 410 and 414 may be displayed on the user interfaces 130 and 140,respectively. Thus, the user interfaces 130 and 140 may include displaycomponents configured to render the data 410 and 414, respectively.

In some embodiments, the system 400 may include one or morenon-transitory computer-readable mediums described above in relation toFIGS. 1-3. Further, the system 400 may include a communicationinterface, a transceiver, a processor, data storage, and/or anauthentication circuit/component of a server device that may take theform of the communication interfaces 112 and/or 232, the transceivers114 and/or 234, the processors 116 and/or 236, the data storage 118and/or 238, and/or the authentication circuit/component 120 and/or 240of the server devices 100 and/or 200, respectively, described above inrelation to FIGS. 1-3.

In some embodiments, a non-transitory computer-readable medium of thesystem 300 may have stored thereon machine-readable instructions.Further, when executed by a server device of the system 300, theinstructions may cause the server device to perform operations. In someinstances, various operations may include receiving, by a communicationinterface of the server device, first activity data 410 associated witha first activity 402 of a first account, such as the user's account.Further, various operations may include receiving second activity data414 associated with a second activity 404 of a second account, such asthe spouse's account. In some instances, various operations may includedetermining, by an authentication circuit of the server device, arelationship between the first account and the second account. Forexample, the authentication circuit may determine the relationshipbetween the user's account and the spouse's account. In some instances,the accounts may, for example, be associated with a spouse-spouserelationship. Further, the accounts may be linked by one or accounts,balances, and/or funds. Further, the accounts may include smartphoneaccounts of smartphones 406 and/or 408, possibly indicating that thesmartphones 406 and 408 are in close proximity to the structures 422,424, 426, and/or 428. In some instances, various operations may includedetermining, by the authentication circuit, an authentication of thesecond activity 404 based at least on the relationship. In someinstances, various operations may include transmitting, by a transmitterof the communication interface, an indication of the authentication ofthe second activity 404 to a client device such as the smartphones 406and/or 408. Yet further, the indication of the authentication may betransmitted to a merchant device at one or more of the stores instructures 422, 424, 426, and/or 428.

In some embodiments, the relationship between the first account and thesecond account may be based on various factors. As noted, therelationship may include a spouse-spouse relationship. Yet further, therelationship may be based on mutual contacts of the user's socialaccount and the spouse's social account. Further, a relationship mayinclude other types of relationships. For example, a relationship mayinclude a parent-child relationship, a parent-parent relationship, aspouse-spouse relationship, a child-child relationship, a friend-friendrelationship, and/or other types of relationships. For example, therelationship between the user's account and the spouse's account mayinclude a parent-parent relationship and/or a friend-friendrelationship. Further, a relationship between the user's account and afriend's account may be used to authenticate activities of the user'saccount and/or the friend's account.

In some embodiments, various operations may include determining, by aprocessor of the server device, that the second activity data 414includes biometric data 416, e.g., fingerprint and/or voice data, toauthenticate the second activity 404. Further, various operations mayinclude determining, by the authentication circuit, the authenticationis a successful authentication of the second activity 404 based at leaston the biometric data 416 to authenticate the second activity.

In some embodiments, determining the relationship between the firstaccount and the second account may include other operations. Forexample, various operations may include determining, by a processor ofthe server device, a first location 418 of the first activity 402 fromthe first activity data 410 and a second location 430 of the secondactivity 404 from the second activity data 414. For example, the firstactivity data 410 and the second activity data 414 may include GPS dataindicating the locations 418 and 430, respectively. Further, the firstactivity data 410 and the second activity data 414 may include storedata of stores in structures 426 and 424, respectively, including storelocation data, store contact data such as a local address, an emailaddress, a website URL, and/or a phone number. Yet further, the firstactivity data 410 and the second activity data 414 may include firstaccount data and second account data, respectively, including purchasingdata, invoice data, product data, shipping data, and/or other datarelated to the activities 402 and 404, respectively. Further,determining the authentication of the second activity 404 may be basedat least on the second location 430 proximately located near the firstlocation 418.

For example, consider the scenario where the system 400 determines aconfidence level to authenticate the second activity 404 based on thesecond location 430 of the spouse's smartphone 408 located proximatelynear the first location 418 of the user's smartphone 406. In suchinstances, the confidence level may meet or exceed a confidencethreshold to authenticate the second activity 404. In variousembodiments, the confidence level and/or the confidence threshold mayinclude the confidence levels and/or confidence thresholds,respectively, described above in relation to FIGS. 1-4.

In some embodiments, determining the relationship between the firstaccount and the second account may include additional operations. Forexample, various operations may include determining, by a processor ofthe server device, a first time of the first activity 402 from the firstactivity data 410 and a second time of the second activity 404 from thesecond activity data 414. In some instances, the first activity data 410and the second activity data 414 may include the first time and thesecond time, respectively, among the other forms of data describedabove. Further, various operations may include determining, by theauthentication circuit, a successful authentication of the firstactivity 402 based at least on the first activity data 410. For example,the authentication circuit may determine the successful authenticationbased on the biometric data 412 including fingerprint or voice data ofthe user. Yet further, various operations may include determining, bythe authentication circuit, the authentication is a successfulauthentication of the second activity 404 based at least on thesuccessful authentication of the first activity and a time differencebetween the first time and the second time. In some instances, the timedifference between the first time and the second time may be a fewminutes, approximately less than an hour, a few hours, and/or longerperiods of time. Yet, in some instances, the time difference may be afew minutes for the system 400 to determine a confidence level tosuccessfully authenticate the second activity 404.

In some embodiments, various operations may include determining, by theauthentication circuit, a confidence level to authenticate the secondactivity 404. In some instances, the confidence level may be based atleast on the relationship between the first account and the secondaccount including the relationship between the user's account and thespouse's account. Further, the confidence level may be based on therelationship between the first location 418 of the first activity 402and the second location 430 of the second activity 404. For example, theconfidence level may range from a forty percent confidence level to aninety percent confidence level based on the relationship betweenaccounts and the relationship between the first location 418 and thesecond location 430. Further, the authentication circuit may determinethat the confidence level meets a confidence threshold. Yet further,various operations may include determining, by the authenticationcircuit, the authentication is a successful authentication of the secondactivity 404 based at least on the confidence level.

In some embodiments, various operations may include determining, by theauthentication circuit, a confidence level to authenticate the secondactivity 404 is below a confidence threshold. For example, consideringone or more scenarios above, the confidence level may be a forty percentconfidence level that is below the confidence threshold of ninety-fivepercent. In some instances, the confidence level may be based at leaston the relationship between the first account and the second accountsuch as the relationship between the user's account and the spouse'saccount. Further, the confidence level may be based on the relationshipbetween the first location 418 of the first activity 402 and the secondlocation 430 of the second activity 404. In addition, various operationsmay include determining, by the authentication circuit, theauthentication is a failed authentication of the second activity 404based at least on the confidence level.

In some embodiments, various operations may include determining, by aprocessor of the server device, a first location 418 of the firstactivity 402 from the first activity data 410 and a second location 430of the second activity 404 from the second activity data 414. In someinstances, the first location 418 and the second location 430 mayinclude one or more historical locations and/or stored′ locationsassociated with the relationship between the first account and thesecond account. For example, the first location 418 and the secondlocation 430 may include a historical location such as a shopping malllocation, a shopping center location, a recreational park location,and/or another location associated with the relationship. Further,considering one or more scenarios above, the historical location may beassociated with the relationship between the user's account and thespouse's account. The historical location may be associated withhistorical activities authenticated of the user's account and thespouse's account. In some instances, various operations may includedetermining, by the authentication circuit, a confidence level toauthenticate the second activity 404 based at least on the one or morehistorical locations possibly including the location 418 and/or 430.Further, various operations may include determining, by theauthentication circuit, the authentication is a successfulauthentication of the second activity 404 based at least on theconfidence level.

FIG. 5 is a flowchart of an exemplary method 500 for determiningauthentications of activities, according to an embodiment. Note that oneor more steps, processes, and methods described herein may be omitted,performed in a different sequence, and/or combined for various types ofapplications.

At step 502, the method 500 includes receiving, by a communicationinterface of a server device, first activity data associated with afirst activity of an account and second activity data associated with asecond activity of the account. For example, the communication interfaceof the server device may take the form of the communication interfaces112 and/or 232 of the server devices 100 and/or 200, respectively,and/or other communication interfaces described above in relation toFIGS. 1-4. In some instances, the communication interface may receivethe first activity data 310 and/or 410 associated with the firstactivity 302 and/or 402, respectively, of an account. Yet further, thecommunication interface may receive the second activity data 312 and/or414 associated with a second activity 304 and/or 404, respectively, ofthe account.

At step 504, the method 500 includes determining, by a processor of theserver device, a first location of the first activity from the firstactivity data and a second location of the second activity from thesecond activity data. For example, the processor of the server devicemay take the form of the processors 116 and/or 236 of the server devices100 and/or 200, respectively, and/or other, processors described abovein relation to FIGS. 1-4. In some instances, the processor may determinea first location 314 and/or 418 of the first activity 302 and/or 402from the first activity data 310 and/or 410, respectively. Further, theprocessor may determine a second location 318 and/or 430 of the secondactivity 304 and/or 404 from the second activity data 312 and/or 414.

At step 506, the method 500 includes determining, by an authenticationcircuit of the server device, a first authentication of the firstactivity based at least on the first activity data. For example, theauthentication circuit of the server device may include authenticationcircuit/component 120 and/or 240 of the server devices 100 and/or 200,respectively, and/or other authentication circuits and/or componentsdescribed above in relation to FIGS. 1-4. In some instances, theauthentication circuit may determine a first authentication of the firstactivity 302 and/or 402 based at least on the first activity data 310and/or 410.

At step 508, the method 500 includes determining, by the authenticationcircuit, a second authentication of the second activity based at leaston the first authentication. For example, the authentication circuit maydetermine a second authentication of the second activity 304 and/or 404based at least on the first authentication of the first activity 302and/or 402, respectively. For example, the first authentication of thefirst activity 302 and/or 402 may correspond to a confidence level forauthenticating the second activity 304 and/or 404, respectively.

At step 510, the method 500 includes causing, by the communicationinterface, a client device to display an indication of the secondauthentication. For example, the client device may take the form ofclient devices 306, 320, 406, 408, and/or other client devices describedabove in relation to FIGS. 1-4. As noted, the client device may take theform of a merchant device, e.g., a tablet device in a merchant storethat displays the indication of the second authentication.

FIG. 6 provides an exemplary client device 600 with a user interface602, according to an embodiment. In some instances, the client device600 may take the form of client devices 306, 420, 406, 408, and/or otherclient devices described above in relation to FIGS. 1-5. Further, theclient device 600 may take the form of a merchant device that displaysindications of authentications of account activities.

As shown, the user interface 602 displays a time 604 indicating acurrent time of “1:10 PM.” Further, the user interface 602 displaysactivity data 606 of an account 608. For example, considering one ormore scenarios above, the account 608 may be the user's account. Yetfurther, the account 608 may be a joint account of the user and theuser's spouse. As such, various account activities of the user and/orthe spouse may be displayed through the activity data 606. Yet,referring back to FIG. 4, activity data 606 may be separated such thatthe user's activities 402 are displayed on the user's smartphone 406 andthe spouse's activities 404 are displayed on the spouse's smartphone408.

In some embodiments, the user interface 602 displays activity data 610that may take the form of the activity data 414 described above inrelation to FIG. 4. The activity data 610 may include biometric data 618that may take the form of the biometric data 416. The activity data 610may include location data 622 that may indicate the location 430 and/orstore data 624 that indicates a store in the structure 424. The activitydata 610 may include data 626 of various details of one or morepurchases made at the store in the structure 424. As shown, the activitydata 610 may also include an indication of the time of the purchase(s)as “12:09 PM.”

In some embodiments, the user interface 602 displays activity data 612that may take the form of the activity data 410. The activity data 612may include biometric data 620 that may take the form of the biometricdata 412. The activity data 612 may include location data 628 that mayindicate the location 418 and/or store data 630 that indicates the storein the structure 426. The activity data 612 may include data 632 ofvarious details of one or more purchases made at the store in thestructure 426. As shown, the data 612 may also include an indication ofthe time of the purchase(s) as “11:14 AM.”

In some embodiments, the user interface 602 displays activity data 614that may take the form of the activity data 312. The activity data 614may include location data 634 that may indicate the location 318 of thefuel dispenser machine 320. The activity data 614 may include data 636indicating various details of the fuel purchased via the fuel dispensermachine 320. As shown, the data 614 may include the time of the purchaseas “10:30 AM.”

In some embodiments, the user interface 602 displays activity data 616that may take the form of the activity data 310. The activity data 616may include location data 638 that may indicate the location 314,possibly the user's home location and/or the location of the vehicle308. The activity data 616 may include data 640 indicating variousdetails of authenticating the user as the driver of the vehicle 308. Asshown, the activity data 616 may include the time, “10:15 AM,” possiblyindicating the time the client device 306 proximately senses the vehicle308. In addition, the user interface 602 includes the scroll 638 to viewvarious other activities associated with the account 608.

FIGS. 7A and 7B provide an exemplary client device 700, according to anembodiment. The client device 700 may take the form of the client device600 and/or other client devices described above in relation to FIGS.1-6. As shown, the client device 700 may take the form of a wearablecomputer. The client device 700 may include a wearable computing devicewith at least one of a head-mountable display and an arm-mountabledisplay. As shown in FIG. 7A, the client device 700 may take the form ofa head-mountable display/device (HMD). The client device 700 may includelenses 702 and 704. The client device 700 may also include a sidecomponent 706, a side component 708, and a middle component 710. Forexample, the computing device 700 may be mountable on a user's head suchthat the side component 706 rests on one ear of the user and the sidecomponent 708 rests on the other ear of the user. Further, the middlecomponent 710 may rest on the nose of the user. In some instances, thelenses 702 and 704 may be positioned in front of the user's eyes.Further, the lenses 702 and 704 may include displays 712 and 714,respectively. In some instances, the displays 712 and 714 may betransparent, partially see-through, and/or configured to provide anaugmented reality. Further, the displays 712 and/or 714 may includetouch sensing displays.

As shown in FIG. 7B, the client device 700 may take the form of anarm-mountable device. For example, the side components 706 and 708, themiddle component 710, and/or the lenses 702 and 704 may be adjustable tofit/mount on an arm and/or wrist 715 of a user. As shown, the lens 702may be mounted/positioned on the top of the wrist 715. The sidecomponents 706, 708, and/or the middle component 710 may be adjusted tofit around the wrist 715. The lens 704 may be mounted/positioned on thebottom of the wrist 715. In some instances, the displays 702 and 704 mayinclude fingerprint sensors configured to receive biometric data 716. Asshown, the lens 702 may be configured to receive the biometric data 716,e.g., fingerprint data, that may take the form of the biometric data 618and/or other biometric data described above in relation to FIGS. 1-6.Further, the lenses 702 and/or 704 may include scanners such as laserscanners configured to scan the eyes of the user to retrieve biometricdata from the user's eyes. Yet further, the lenses 702 and/or 704 may beconfigured to detect one or more patterns of pulses from the wrist 715of the user.

In some instances, referring back to FIG. 5, the method 500 may includecausing the client device to display the indication of anauthentication. For example, the client device 700 may displayindications of authentications. As noted, for example, theauthentication circuit of the server may determine first and secondauthentications of the first and second activities, respectively. Insome instances, the method 600 may include causing the client device 700to display the indication of the second authentication. As shown, thedisplays 712 and/or 714 may display the indication of the secondauthentication to a user wearing the client device 700.

In some embodiments, an authentication scheme may involve one or moreforms of biometric data to authenticate activities of an account. Insome instances, the authentication scheme may require different forms ofbiometric data at different locations. For example, a user may wish tomake a purchase at a given store. Further, an authentication scheme maycause a merchant device to a request a left thumbprint from the user toauthenticate the purchase at the store. Further, another store mayrequest a right thumbprint to authenticate purchases by the user. Insome instances, the authentication scheme may require different forms ofbiometric data at different times. For example, the authenticationscheme may require a left thumbprint to authenticate activities onMonday through Thursday. Further, the authentication scheme may requirea right thumbprint on Friday through Sunday. As such, the authenticationscheme may maintain and/or increase confidence levels for authenticatingactivities of the account, without the need for providing cards, codes,and/or other forms of account information.

In some embodiments, an authentication scheme may be selected toauthenticate activities of an account. For example, a user may select anauthentication scheme that requires authentication data of a left and/orright thumbprint, an iris scan of a left and/or right eye, a pattern ofpulses, a size/shape of a body, voice recognition, and/or otherbiometric data. In some instances, the user may select and/or modify theone or more authentication schemes to authenticate the activities of theaccount. For example, referring back to FIG. 3, the user may select anauthentication scheme that requires the left thumbprint to authenticatecertain activities such as unlocking the vehicle 308. In particular, thevehicle 308 may include a fingerprint sensor device to receive thethumbprint data. Further, the selected authentication scheme may requirean iris scan of the user's right eye to authenticate fuel purchases fromthe fuel dispenser machine 320. Yet further, the selected authenticationscheme may require a given pattern of pulses to authenticate purchasesat various stores in the structures 422-428.

FIG. 8 is an illustration of various authentication schemes 800,according to an embodiment. As shown, one or more authentication schemes800 may include an authentication scheme 802 that requires biometricdata 808 and/or 810. For example, the biometric data 808 and 810 maytake the form of the biometric data 412 and 416, respectively, describedabove in relation to FIG. 4. Further, the biometric data 808 may includefingerprint data of a left finger and the biometric data 810 may includefingerprint data of a right finger. Further, as shown, one or moreauthentication schemes 800 may include an authentication scheme 804 thatrequires biometric data 812 and/or 814. For example, the biometric data812 may include eye and/or iris data of a left eye and the biometricdata 814 may include eye and/or iris data of a right eye. In addition,as shown one or more authentication schemes 800 may include anauthentication scheme 806 that requires biometric data 816. For example,biometric data 810 may include pulse data, possibly detectable from auser's wrist and/or head.

In some embodiments, a system may determine an authentication scheme. Insome instances, the system may include a communication interface, atransceiver, a processor, data storage, and/or an authenticationcircuit/component of a server device that may take the form of thecommunication interfaces 112 and/or 232, the transceivers 114 and/or234, the processors 116 and/or 236, the data storage 118 and/or 238,and/or the authentication circuit/component 120 and/or 240 of the serverdevices 100 and/or 200, respectively, described above in relation toFIGS. 1-2B. Further, the system may determine the authentication schemeusing one or more other circuits/components described above in relationto FIGS. 1-7. For example, the system may determine the authenticationscheme via the client device 700 that may take the form of ahead-mountable device and/or an arm-mountable device.

In some embodiments, the system may include the communication interfaceof the server device that receives a selection of an authenticationscheme to authenticate activities of an account. For example, theauthentication scheme may be selected from the authentication schemes802, 804, 806, and/or a combination of such schemes. Further, thecommunication interface may receive activity data associated with agiven activity of the account. In some instances, the activity data maytake the form of activity data 606, 610, 612, 614, 616, and/or otheractivity data described above in relation to FIGS. 1-7.

Yet further, a processor of the server device may determine the activitydata includes biometric data to authenticate the given activity of theaccount. In addition, the authentication circuit of the server devicemay determine the authentication scheme is selected from a number ofauthentication schemes 800, 802, 804, and/or 806, where the selectedauthentication scheme requires one or more of biometric data 808, 810,812, 814, and/or 816 to authenticate the activities of the account.Further, the authentication circuit may determine an authentication ofthe given activity based at least on one or more of the biometric data808, 810, 812, 814, and/or 816. Yet further, a transmitter of thecommunication interface may transmit an indication of the authenticationto a client device such as the client device 700.

In some embodiments, the biometric data that authenticates the givenactivity includes first fingerprint data 808 and second fingerprint data810. For example, referring back to FIG. 7, the lens 702 may beconfigured to receive the first fingerprint data 808 and the secondfingerprint data 810 to authenticate the given activity. In someembodiments, the biometric data that authenticates the given activitymay include at least one of the following: fingerprint data 808 and/or810, eye data 812 and/or 814, pulse data 816, voice data, body data,and/or other biometric data. The authentication circuit may determinethe authentication is a successful authentication of the given activitybased at least on the biometric data.

In some embodiments, the selected authentication scheme may beconfigured to authenticate the activities of the account for a timeperiod. For example, the time period may be a few seconds, minutes,hours, days, weeks, and/or other periods of time. In one scenario, theauthentication scheme 802 may be selected to authenticate activities ofthe account for a time period of few hours and/or days and then theauthentication scheme 804 may be selected to authenticate additionalactivities for a time period of few hours and/or days. In someinstances, the authentication circuit may determine from the activitydata that the given activity occurred during the time period. Theauthentication circuit may determine the authentication is a successfulauthentication of the given activity based at least on the givenactivity that occurred during the time period.

FIG. 9 is an exemplary system 900, according to an embodiment. As shown,activities 902 and 904 may involve a smartphone 906 and/or a vehicle908. For example, considering one or more of the scenarios above, thesystem 900 may determine the activity 902 of a user leaving a homelocation and carrying the smartphone 906 to the vehicle 908. Further,the activity 902 may include the user entering the vehicle 908 at alocation 914 provided on a map 916 for illustrative purposes. Yetfurther, the activity 902 may include the user carrying the smartphone906 and driving proximate to structures 920, 922, 924, and/or 926provided on the map 916. In addition, the activity 904 may include theuser carrying the smartphone 906 proximate to structures 920, 922, 924,and/or 926. The smartphone 906 may, for example, take the form of clientdevice 306 in relation to FIG. 3 and/or other client devices describedabove in relation to FIGS. 1-8. For example, the client device 906 maytake the form of client device 104 such that activity data 910 may bedisplayed on the user interface 130. Thus, the user interface 130 mayinclude a display component configured to display the activity data 910.

In some embodiments, the system 900 may include a communicationinterface, a transceiver, a processor, data storage, and/or anauthentication circuit/component of a server device that may take theform of the communication interfaces 112 and/or 232, the transceivers114 and/or 234, the processors 116 and/or 236, the data storage 118and/or 238, and/or the authentication circuit/component 120 and/or 240of the server devices 100 and/or 200, respectively, described above inrelation to FIGS. 1-2B. Further, the system 900 may receive a selectionof one or more authentication schemes to authenticate activities 902and/or 904 of an account. For example, the selected authenticationscheme may include one or more authentication schemes 800, 802, 804,and/or 806.

In some embodiments, the selected authentication scheme may beconfigured to authenticate the activities of the account for a firsttime period and a second time period. For example, the selectedauthentication may be configured to authenticate the activity 902 of theaccount for the first time period. Further, the selected authenticationmay be configured to authenticate the activity 904 of the account forthe second time period. In some instances, the selected authenticationscheme may require the authentication data 910 including biometric datato authenticate the activity 902 during the first time period. Further,the authentication scheme may require the authentication data includingthe biometric data 928 to authenticate the activity 904 during thesecond time period.

In some embodiments, the selection of the authentication scheme mayinclude an indication of a time period to authenticate the activities ofthe account. For example, an authentication scheme may be selected and aright thumbprint, e.g., the biometric data 928, may be required toauthenticate the activity 904 for a given day while shopping at storesin structures 920, 922, 924, and/or 926. In some instances, theauthentication circuit of the system 900 may determine from the activitydata 912 that the given activity 904 occurred during the time period.For example, the activity data 912 may include time data of one or morepurchases from the stores in the structures 920-926. Further, theauthentication circuit may determine the authentication is a successfulauthentication of the given activity 904 based at least on the givenactivity 904 occurring during the time period.

In some embodiments, the communication interface of the system 900 mayreceive second activity data 912 associated with a second activity 904of the account. For example, consider a scenario where an unauthorizeduser attempts to purchase items at a store in the structure 922 usingsecond biometric data of the unauthorized user. In some instances, theprocessor of the system 900 may determine the second activity data 912includes the second biometric data to authenticate the second activity904 of the account. Further, the authentication circuit of the system900 may determine the second authentication is a failed authenticationof the second activity 904 based at least on the second biometric dataof the unauthorized user. In some embodiments, the authenticationcircuit may determine a difference between the biometric data 928 andthe second biometric data of the unauthorized user. Further, theauthentication circuit may determine the second authentication is thefailed authentication based at least on the difference between thebiometric data 928 and the second biometric data of the unauthorizeduser.

FIG. 10 is an exemplary system 1000, according to an embodiment. In someembodiments, the system 1000 may include one or more non-transitorycomputer-readable mediums described above in relation to FIGS. 1-9.Further, the system 1000 may include a communication interface, atransceiver, a processor, data storage, and/or an authenticationcircuit/component of a server device that may take the form of thecommunication interfaces 112 and/or 232, the transceivers 114 and/or234, the processors 116 and/or 236, the data storage 118 and/or 238,and/or the authentication circuit/component 120 and/or 240 of the serverdevices 100 and/or 200, respectively, described above in relation toFIGS. 1-2B.

As shown, activities 1002 and 1004 may involve a client device 1006 thatmay, for example, take the form of the client device 906 described abovein relation to FIG. 9. For example, considering one or more of thescenarios above, the system 1000 may determine an activity 1002 of auser carrying the client device 1006 at a location 1012 proximate to astructure 1022. As shown, the structures 1022, 1024, 1026, and/or 1028may be provided on a map 1014 for illustrative purposes. In someinstances, the structures 1022, 1024, 1026, and/or 1028 may take theform of the structures 920, 922, 924, and/or 926, respectively,described above in relation to FIG. 9.

In some embodiments, the system 1000 may determine an authentication ofthe activity 1002 including a purchase at a store in the structure 1022.The system 1000 may determine the authentication based on anauthentication scheme that requires biometric data 1010. For example,referring back to FIGS. 8-9, the selected authentication scheme mayinclude the authentication scheme 802 that requires biometric data 808and/or 810 to authenticate the activity 1002. As shown, the biometricdata 1010 may take the form of the biometric data 810 that includesfingerprint data. In some instances, the user may place a finger on afingerprint sensor of a merchant device in the store to make thepurchase. The system 1000 may determine an authentication of theactivity 1002 based on the biometric data 1010 received in the activitydata 1008, thereby circumventing the need for providing cards, codes,and/or other forms of account data to authenticate the activity 1012 ofmaking one or more purchases.

In some embodiments, the system 1000 may determine an authentication ofthe activity 1004 that includes a transaction at the structure 1028. Insome instances, the structure 1028 may include a bank. Further, thesystem 1000 may determine the authentication based on a selectedauthentication scheme that requires biometric data 1018 that may includeeye and/or iris data. The authentication scheme may require biometricdata 1018 based on the transaction at the structure 1028, possibly forwithdrawing money. For example, referring back to FIGS. 8-9, theselected authentication scheme may include the authentication scheme 804that requires biometric data 812 and/or 814 to authenticate the activity1004. In some instances, the user may position one or more eyes in frontof an eye and/or iris scanner of a merchant device in the bank. Thesystem 1010 may determine the authentication of the activity 1004 basedon the biometric data 1018 received in the activity data 1016, therebycircumventing the need for providing cards, codes, and/or other forms ofaccount data to authenticate the activity 1012 of withdrawing money fromthe account.

In some embodiments, a non-transitory computer-readable medium of thesystem 1000 may have stored thereon machine-readable instructions.Further, when executed by a server device of the system 1000, theinstructions may cause the server device to perform operations. In someinstances, various operations may include receiving, by a communicationinterface of the server device, the activity data 1008 associated withthe given activity 1002 of the account. Further, the operations mayinclude determining, by an authentication circuit of the server device,an authentication scheme to authenticate activities of the account,where the authentication scheme requires the biometric data 1010 toauthenticate the activities of the account. Yet further, the operationsmay include determining, by a processor of the server device, theactivity data 1008 includes the biometric data 1010 to authenticate thegiven activity 1002 of the account. In addition, the operations mayinclude determining, by the authentication circuit, an authentication ofthe given activity 1002 based at least on the biometric data 1010.Further, the operations may include transmitting, by a transmitter ofthe communication interface, an indication of the authentication to theclient device 1006 and/or a merchant device at the store in thestructure 1022.

In some embodiments, the authentication scheme may be determined basedon a number of factors. In some instances, the authentication scheme maybe determined based on a time. For example, the authentication schememay be determined based on a current time matching a predetermined time.In one scenario, a given authentication scheme may be determined forMonday through Thursday and another authentication scheme may bedetermined for Friday through Sunday. As shown in FIG. 10, theauthentication scheme requiring biometric data 1010 may be determinedbased on a first time of the activity 1002 occurring withinpredetermined time period. The biometric data 1010 may includefingerprint data from the left hand data and/or right hand data.Further, the authentication scheme requiring the biometric data 1018 maybe determined based on a second time of the activity 1004 occurringwithin another predetermined time period.

In some embodiments, determining the authentication scheme toauthenticate the activities of the account may include determining acurrent time, a current date, a current day of a week, a current month,a current season, a time of a future event, a date of the future event,a day of the future event, a month of the future event, a season of thefuture event, a time of a past event, a date of the past event, a daythe past event, a month of the past event, and/or a season of the pastevent. The authentication scheme may be determined based on one or moreof the times being within one or more of the time periods. For example,the authentication scheme may be determined based on the current timebeing within a date of the future event.

In some embodiments, the authentication scheme may be determined basedon a location. For example, the authentication scheme requiringbiometric data 1010 may be determined based on the location 1012.Further, the authentication scheme requiring the biometric data 1018 maybe determined based on the location 1020. In some instances, determiningthe authentication scheme to authenticate the activities of the accountmay include determining a current location, a past location, a futurelocation, a location between the client device 1006 and an authorizeduser of the account, and/or other factors.

In some embodiments, determining the authentication scheme toauthenticate the activities of the account may include determining anambient temperature, a weather forecast at the current location, e.g.,the locations 1012 and/or 1020, a weather forecast proximate to aplanned location of a planned event, a past weather forecast proximateto a past location of the past event, information on a calendarassociated with the account, information accessible via a socialnetworking account associated with the account, biometric statisticsassociated with the account, noise level or any recognizable soundsdetected by the client device 1006, other client devices of the system1000 such as merchant devices, the other client devices proximate to theclient device 1012, and/or the other client devices that are availableto communicate with the server device.

In some embodiments, the authentication scheme may be configured toauthenticate the activities of the account for a first time period and asecond time period. For example, referring back to FIG. 9, theauthentication scheme may require biometric data 928 that includesfingerprint data of a left hand to authenticate the activities duringthe first time period. Yet further, the authentication scheme mayrequire biometric data 1010 that includes fingerprint data of a righthand to authenticate the activities during the second time period.

In some embodiments, the system may determine from activity data that agiven activity occurs during a time period. In some instances, variousoperations may include determining, by the authentication circuit, theauthentication scheme is one of a number of authentication schemes ofthe account. For example, referring back to FIG. 8, the authenticationscheme may be one of a number of the authentication schemes 802, 804,806, and/or a combination of such schemes. The authentication schemesmay be configured to authenticate the activities of the account for atime period. Yet further, the operations may include determining fromthe activity data 1008 that the activity 1002 occurred during the timeperiod. For example, the activity data 1008 may include one or moretimes, dates, weeks, months, and/or years associated with the activity1002. In addition, the operations may include determining theauthentication is a successful authentication of the given activity 1002based at least on the activity 1002 occurring during the time period.

In some embodiments, various operations may include determining, by theauthentication circuit, the authentication scheme is one of a pluralityof authentication schemes of the account. Further, the authenticationscheme may be configured to authenticate the activities proximate to thelocation 1012. Yet further, the operations may include determining fromthe activity data 1008 that the activity 1002 occurred proximate to thelocation 1012. In addition, the operations may include determining theauthentication is a successful authentication of the given activity 1002based at least on the given activity 1002 occurring proximate to thelocation 1012.

In some embodiments, the determined authentication scheme may requirethe biometric data 1010. For example, various operations may includereceiving, by the communication interface, second activity data 1016associated with a second activity 1004 of the account. Further, theoperations may include determining, by the processor, the secondactivity data 1016 includes second biometric data to authenticate thesecond activity 1004 of the account. In some instances, the secondbiometric data may include biometric data 928 that differs from thebiometric data 1010 required to authenticate activities of the account.Thus, the operations may include determining, by the authenticationcircuit, the second authentication is a failed authentication of thesecond activity 1004 based at least on the second biometric data thatdiffers from the biometric data 1010. In addition, the operations mayinclude determining the second authentication is a successfulauthentication of the second activity 1004 based at least on determiningthe second activity data 1016 includes the biometric data 1010.

In some embodiments, the operations may include determining, by theauthentication circuit, a difference between the biometric data 1010 andthe second biometric data 928. Further, the operations may includedetermining the second authentication is the failed authentication basedat least on the difference between the biometric data 1010 and thesecond biometric data 928.

FIG. 11 provides an exemplary client device 1100 with a user interface1102, according to an embodiment. In some instances, the client device1100 may take the form of client device 600, 700, and/or other clientdevices described above in relation to FIGS. 1-10. Further, the clientdevice 1100 may take the form of a merchant device that displaysindications of authentications.

As shown, the user interface 1102 displays a time 1104 indicating acurrent time of “3:10 PM.” Further, the user interface 1102 displaysactivity data 1106 of an account 1108. For example, considering one ormore scenarios above, the account 1108 may be the user's account. Assuch, various activities of the user's account 1108 may be displayedthrough the activity data 1106.

In some embodiments, the user interface 1102 displays activity data 1110that may take the form of the activity data 1016 described above inrelation to FIG. 10. The activity data 1110 may include biometric data1116 that may take the form of the biometric data 1018. The activitydata 1110 may include location data 1122 that may indicate the location1020 and/or store data 1124 that indicates the store in the structure1028. The activity data 1110 may include data 1126 of various details ofone or more purchases made at the store in the structure 1028. As shown,the activity data 1110 may also include an indication of the time of thepurchase(s) as “2:45 PM.”

In some embodiments, the user interface 1102 displays activity data 1112that may take the form of the activity data 1008. The activity data 1112may include biometric data 1118 that may take the form of the biometricdata 1010. The activity data 1112 may include location data 1128 thatmay indicate the location 1012 and/or store data 1130 that indicates thestore in the structure 1022. The activity data 1112 may include data1132 of various details of one or more purchases made at the store inthe structure 1022. As shown, the activity data 1112 may also include anindication of the time of the purchase(s) as “2:05 PM.”

In some embodiments, the user interface 1102 displays activity data 1114that may take the form of the activity data 912. The activity data 1114may include location data 1134 that may indicate the location 918 and/orstore data 1136 that indicates store data 1136 that may indicate thestore in the structure 922. The activity data 1114 may include data 1138of various details of one or more purchases made at the store in thestructure 922. As shown, the activity data 1114 may include the time ofthe purchase as “1:52 PM.” In addition, the user interface 1102 includesthe scroll 1140 to view various other activities associated with theaccount 1108. For example, the user interface 1102 may display theactivity data 910 associated with the activity 902.

FIG. 12 is a flowchart of an exemplary method 1200 for determining anauthentication scheme to authenticate activities, according to anembodiment. Note that one or more steps, processes, and methodsdescribed herein may be omitted, performed in a different sequence,and/or combined for various types of applications.

At step 1202, the method 1200 may include receiving, by a communicationinterface of a server device, activity data associated with an activityof the account. For example, the communication interface of the serverdevice may take the form of the communication interfaces 112 and/or 232of the server devices 100 and/or 200, respectively, and/or othercommunication interfaces described above in relation to FIGS. 1-11. Insome instances, the communication interface may receive the activitydata 910 and/or 912 associated with the activity 902 and/or 904,respectively, of the account. Yet further, the communication interfacemay receive the activity data 1008 and/or 1016 associated with theactivity 1002 and/or 1004, respectively, of the account.

At step 1204, the method 1200 may include determining an authenticationscheme to authenticate activities of the account, where theauthentication scheme requires authentication data to authenticate theactivities of the account. The authentication scheme may be determinedin any manner described above in relation to FIGS. 8-11. In someinstances, the authentication scheme may be determined based on theactivity of the account. For example, the authentication scheme 802 maybe determined to authenticate purchases at one or more stores. Further,the authentication scheme 804 may be determined to authenticatetransactions with the account such as withdrawals from the account at abank and/or an ATM machine. In some instances, a combination of theauthentication schemes 802-806 may be determined to authenticate variousactivities of the account. For example, an authentication scheme mayrequire a left thumbprint for authenticating various activities and aright thumbprint for authenticating other activities.

In some embodiments, the authentication data may include account data,e.g., ATM card data, credit card data, identification card data such asdriver's license data, a PIN number, a zip code, a password, and/orother forms of account data. In some embodiments, the authenticationdata may include biometric data. For example, the authentication datamay include biometric data 808-816 as described above in relation toFIGS. 8-11. In some instances, and the biometric data 808 may includeleft finger data and the biometric data 810 may include right fingerdata.

At step 1206, the method 1200 may include determining, by a processor ofthe server device, the activity data includes the authentication data toauthenticate the given activity of the account. For example, theprocessor of the server device may take the form of the processors 116and/or 236 of the server devices 100 and/or 200, respectively, and/orother processors described above in relation to FIGS. 1-11. Referringback to FIG. 10, the processor may determine that the activity data 1008includes the authentication data, e.g., biometric data 1010, toauthenticate the given activity 1002 of the account. Further, theprocessor may determine that the activity data 1016 includes theauthentication data, e.g., 1018, to authenticate the given activity 1004of the account.

At step 1208, the method 1200 may include determining, by anauthentication circuit, an authentication of the given activity based atleast on the authentication data. For example, the authenticationcircuit of the server device may include authenticationcircuit/component 120 and/or 240 of the server devices 100 and/or 200,respectively, and/or other authentication circuits/components describedabove in relation to FIGS. 1-4. In some instances, the authenticationcircuit may determine the authentication of the given activity 1002based on the authentication data 1008 that may include the biometricdata 1010. Further, the authentication circuit may determine theauthentication of the given activity 1004 based on the authenticationdata 1016 that may include the biometric data 1018.

At step 1210, the method 1200 may include transmitting, by a transmitterof the communication interface, an indication of the authentication to aclient device. For example, the client device may take the form ofclient devices 700, 906, 1006, and/or other client devices describedabove in relation to FIGS. 1-11. As noted, the client device may takethe form of a merchant device, e.g., a tablet device in a merchant storethat displays the indication of the authentication. For example, themerchant device may display the indications of the authenticationssimilar to that of the user interface 1102 described above in relationFIG. 11.

In some embodiments, the authentication scheme may be configured toauthenticate the activities of the account for a first time period and asecond time period. For example, referring back to FIGS. 9 and 10, theauthentication scheme may authenticate the activity 904 for a first timeperiod and the activity 1002 for a second time period. In someinstances, the authentication scheme may require left finger data, e.g.,biometric data 928, to authenticate the activities 904 during the firsttime period. Further, the authentication scheme may require right fingerdata, e.g., the biometric data 1010, to authenticate the activities 1002during the second time period.

In some embodiments, the method 1200 may include determining, by theauthentication circuit, the authentication scheme is one of a number ofauthentication schemes of the account. For example, referring back toFIGS. 8-9, the authentication scheme may be one of a number ofauthentication schemes 802, 804, and/or 806. In some instances, theauthentication scheme may be configured to authenticate the activities904 of the account for a time period. The time period may include one ormore time periods described above in relation to FIGS. 8-11. Further,the method 1200 may include determining from the activity data 912 thatthe given activity 904 occurred during the time period and determiningthe authentication is a successful authentication of the given activity904 based at least on the given activity 904 occurring during the timeperiod.

In some embodiments, a system may include a communication interface of aserver device with means for receiving a selection of an authenticationscheme to authenticate activities of an account and receiving activitydata associated with a given activity of the account. The system mayinclude a processor of the server device with means for determining theactivity data includes biometric data to authenticate the given activityof the account. The system may include an authentication circuit of theserver device with means for determining the authentication scheme isselected from a plurality of authentication schemes, where the selectedauthentication scheme requires the biometric data to authenticate theactivities of the account. The system may include the authenticationcircuit of the server device with means for determining anauthentication of the given activity based at least on the biometricdata. The system may include a transmitter of the communicationinterface with means for transmitting an indication of theauthentication to a client device.

In some embodiments, a system may include a communication interface of aserver device with means for receiving first activity data associatedwith a first activity of an account and second activity data associatedwith a second activity of the account. The system may include aprocessor of the server device with means for determining a firstlocation of the first activity from the first activity data and a secondlocation of the second activity from the second activity data. Thesystem may include an authentication circuit of the server device withmeans for determining a first authentication of the first activity basedat least on the first activity data. The system may include theauthentication circuit of the server device with means for determining asecond authentication of the second activity based on at least one ofthe first authentication, the first location, and the second location.The system may include a transmitter of the communication interface withmeans for transmitting an indication of the second authentication to aclient device.

The above details description describes various features and functionsof the disclosed systems, devices, mediums, and/or methods withreference to the accompanying figures. It should be readily understoodthat the aspects of the present disclosure, as generally describedherein, and illustrated in the figures, can be arranged, substituted,combined, separated, and designed in a wide variety of differentconfigurations, all of which may be contemplated herein.

With respect to any or all of the message flow diagrams, scenarios, andflow charts in the figures and as discussed herein, each step, blockand/or communication may represent processing of information and/or atransmission of information in accordance with example embodiments.Alternative embodiments are included within the scope of these exampleembodiments. In these alternative embodiments, for example, functionsdescribed as steps, blocks, transmissions, communications, requests,responses, and/or messages may be executed out of order from that shownor discussed, including in substantially concurrent or in reverse order,depending on the functionality involved. Further, more or fewer steps,blocks and/or functions may be used with any of the message flowdiagrams, scenarios, and flow charts discussed herein, and these messageflow diagrams, scenarios, and flow charts may be combined with oneanother, in part or in whole.

A step or block that represents a processing of information maycorrespond to circuitry that can be configured to perform the specificlogical functions of a herein-described method or technique.Alternatively or additionally, a step or block that represents aprocessing of information may correspond to a module, a segment, or aportion of program code (including related data). The program code mayinclude one or more instructions executable by a processor forimplementing specific logical functions or actions in the method ortechnique. The program code and/or related data may be stored on anytype of computer-readable medium such as a storage device including adisk or hard drive or other storage media.

The computer-readable medium may also include non-transitorycomputer-readable media such as media that stores data for short periodsof time like register memory, processor cache, and/or random accessmemory (RAM). The computer-readable medium may also includenon-transitory computer-readable media such as media that may storeprogram code and/or data for longer periods of time, such as secondaryor persistent long term storage, like read-only memory (ROM), optical ormagnetic disks, and/or compact-disc read only memory (CD-ROM), forexample. Thus, various forms of computer readable media include, forexample, floppy disk, flexible disk, hard disk, magnetic tape, any othermagnetic medium, CD-ROM, any other optical medium, punch cards, papertape, any other physical medium with patterns of holes, RAM, PROM,EEPROM, FLASH-EEPROM, any other memory chip or cartridge, or any othermedium from which a computer is adapted to read. Moreover, a step orblock that represents one or more information transmissions maycorrespond to information transmissions between software and/or hardwaremodules in the same physical device. Further, other informationtransmissions may be between software modules and/or hardware modules indifferent physical devices.

In various embodiments of the present disclosure, execution ofinstruction sequences to practice the present disclosure may beperformed by a computer system. In various other embodiments of thepresent disclosure, a plurality of computer systems coupled by acommunication link to the network (e.g., such as a LAN, WLAN, PSTN,and/or various other wired or wireless networks, includingtelecommunications, mobile, and cellular phone networks) may performinstruction sequences to practice the present disclosure in coordinationwith one another.

Where applicable, various embodiments provided by the present disclosureand the accompanying figures may be implemented using hardware,software, or combinations of hardware and software. Also, whereapplicable, the various hardware components and/or software componentsset forth herein may be combined into composite components comprisingsoftware, hardware, and/or both without departing from the spirit of thepresent disclosure. Where applicable, the various hardware componentsand/or software components set forth herein may be separated intosub-components comprising software, hardware, or both without departingfrom the scope of the present disclosure. In addition, where applicable,it is contemplated that software components may be implemented ashardware components and vice-versa.

Software, in accordance with the present disclosure, such as programcode and/or data, may be stored on one or more computer readablemediums. It is also contemplated that software identified herein may beimplemented using one or more general purpose or specific purposecomputers and/or computer systems, networked and/or otherwise. Whereapplicable, the ordering of various steps described herein may bechanged, combined into composite steps, and/or separated into sub-stepsto provide features described herein.

The present disclosure, the accompanying figures, and the claims are notintended to limit the present disclosure to the precise forms orparticular fields of use disclosed. As such, it is contemplated thatvarious alternate embodiments and/or modifications to the presentdisclosure, whether explicitly described or implied herein, are possiblein light of the disclosure. Having thus described embodiments of thepresent disclosure, persons of ordinary skill in the art will recognizethat changes may be made in form and detail without departing from thescope of the present disclosure.

What is claimed is:
 1. A system, comprising: a non-transitory memory;and one or more hardware processors coupled to the non-transitory memoryand configured to read instructions from the non-transitory memory tocause the system to perform operations comprising: accessing firstactivity data that indicates a first activity corresponding to a usercarrying a client device at a home location; accessing second activitydata that indicates a second activity corresponding to a purchase withan account of the user based at least on user data transferred to amerchant device; determining the home location from the first activitydata and a second location of the purchase from the second activitydata; determining a first authentication of the first activity based atleast on the home location associated with the account; determining asecond authentication of the purchase based on the first authentication,the home location, and the second location; and transmitting anindication of the second authentication to the client device, whereinthe operations further comprise: determining a route located between thehome location and the second location that corresponds to a stored routeassociated with the account; and determining a confidence level toauthenticate the purchase based at least on the route, wherein thesecond authentication is determined to be a successful authentication ofthe purchase based at least on the confidence level.
 2. The system ofclaim 1, wherein the operations further comprise: determining the firstauthentication is a successful authentication of the first activitybased at least on the first activity data; and determining the secondauthentication is a successful authentication of the purchase based atleast on the successful authentication of the first activity.
 3. Thesystem of claim 1, wherein the operations further comprise: determiningthe user data transferred to the merchant device comprises biometricdata to authenticate the purchase; and determining the secondauthentication is a successful authentication of the purchase based atleast on the biometric data.
 4. The system of claim 1, wherein theoperations further comprise: determining a route taken by the clientdevice from the home location to the second location, and wherein thesecond authentication is determined for the purchase based further onthe route of the client device taken from the home location to thesecond location.
 5. The system of claim 1, wherein the operationsfurther comprise: determining the confidence level meets a confidencethreshold, and wherein the second authentication is determined to be asuccessful authentication of the purchase based at least on theconfidence level determined to meet the confidence threshold.
 6. Thesystem of claim 1, wherein the operations further comprise: determiningthe confidence level is below a confidence threshold, and wherein thesecond authentication is determined to be a failed authentication of thepurchase based at least on the confidence level determined below theconfidence threshold.
 7. The system of claim 1, wherein the operationsfurther comprise: determining a route located between the home locationand the second location; determining the route indicates a historicalroute that is one of a plurality of historical routes associated withthe account.
 8. The system of claim 7, wherein the operations furthercomprise: determining a confidence level to authenticate the purchasebased at least on the route that indicates the historical route; anddetermining the second authentication is a successful authentication ofthe purchase based at least on the confidence level.
 9. A non-transitorymachine-readable medium having stored thereon machine-readableinstructions executable to cause a machine to perform operationscomprising: accessing, by a communication interface of the machine,first activity data that indicates a first activity of a first accountand second activity data that indicates a second activity of a secondaccount, wherein the first activity is associated with a home location,and wherein the second activity corresponds to a purchase with thesecond account based at least on user data transferred to a merchantdevice; determining, by an authentication circuit of the machine, arelationship between the first account and the second account;determining, by the authentication circuit, an authentication of thepurchase based at least on an authentication of the first activityassociated with the home location and the relationship between the firstaccount and the second account; and transmitting, by the communicationinterface, an indication of the authentication of the purchase to aclient device with access to the second account, wherein the operationsfurther comprise: determining a route located between the home locationand the second location that corresponds to a stored route associatedwith the account; and determining a confidence level to authenticate thepurchase based at least on the route, wherein the second authenticationis determined to be a successful authentication of the purchase based atleast on the confidence level.
 10. The non-transitory machine-readablemedium of claim 9, wherein the relationship between the first accountand the second account is at least one of the following: a parent-childrelationship, a parent-parent relationship, a child-child relationship,or a friend-friend relationship.
 11. The non-transitory machine-readablemedium of claim 9, the operations further comprising: determining, by aprocessor of the machine, the user data comprises biometric data toauthenticate the purchase; and determining, by the authenticationcircuit, the authentication is a successful authentication of thepurchase based at least on the biometric data to authenticate thepurchase.
 12. The non-transitory machine-readable medium of claim 9,wherein determining the relationship comprises: determining, by aprocessor of the machine, the home location from the first activity dataand a second location of the purchase from the second activity data, andwherein the authentication of the purchase is determined based at leaston the second location proximately located near the home location. 13.The non-transitory machine-readable medium of claim 9, whereindetermining the relationship comprises determining a first time of thefirst activity from the first activity data and a second time of thepurchase from the second activity data, the operations furthercomprising: determining, by the authentication circuit, theauthentication of the first activity is a successful authentication ofthe first activity based at least on the home location; and determining,by the authentication circuit, the authentication of the purchase is asuccessful authentication of the purchase based at least on thesuccessful authentication of the first activity and a time differencedetermined between the first time and the second time.
 14. Thenon-transitory machine-readable medium of claim 9, the operationsfurther comprising: determining, by the authentication circuit, aconfidence level to authenticate the purchase meets a confidencethreshold, wherein the confidence level is based at least on therelationship between the first account and the second account; anddetermining, by the authentication circuit, the authentication of thepurchase is a successful authentication of the purchase based at leaston the confidence level that meets the confidence threshold.
 15. Thenon-transitory machine-readable medium of claim 9, the operationsfurther comprising: determining, by the authentication circuit, aconfidence level to authenticate the purchase is below a confidencethreshold, wherein the confidence level is based at least on therelationship between the first account and the second account; anddetermining, by the authentication circuit, the authentication is afailed authentication of the purchase based at least on the confidencelevel that is below the confidence threshold.
 16. The non-transitorymachine-readable medium of claim 9, the operations further comprising:determining, by a processor of the machine, the home location of thefirst activity from the first activity data and a second location of thepurchase from the second activity data, wherein the home location andthe second location include one or more historical locations associatedwith the relationship; determining, by the authentication circuit, aconfidence level to authenticate the purchase based at least on the oneor more historical locations; and determining, by the authenticationcircuit, the authentication is a successful authentication of thepurchase based at least on the confidence level.
 17. A method,comprising: receiving, by a communication interface of a server device,first activity data associated with a first activity of an account andsecond activity data associated with a second activity of the account,wherein the second activity comprises a purchase with the account basedat least on user data transferred to a merchant device; determining, byone or more processors of the server device, a home location of thefirst activity with the first account and a second location of thepurchase from the second activity data; determining, by anauthentication circuit of the server device, a first authentication ofthe first activity based at least on the home location; determining, bythe authentication circuit, a second authentication of the purchasebased at least on the first authentication based at least on the homelocation; and causing, by the communication interface, the client deviceto display an indication of the second authentication, wherein theoperations further comprise: determining a route located between thehome location and the second location that corresponds to a stored routeassociated with the account; and determining a confidence level toauthenticate the purchase based at least on the route, wherein thesecond authentication is determined to be a successful authentication ofthe purchase based at least on the confidence level.
 18. The method ofclaim 17, wherein the client device is a wearable computing device withat least one of a head-mountable display or an arm-mountable display,and wherein causing the client device to display the indication of thesecond authentication comprises causing the wearable computing device todisplay the indication of the second authentication.